What

Amends the TaskRunResponse schema in api-reference/openapi/releases.json with a new nullable title field: the originating scheduled task's title, when resolvable. Purely additive (+5 lines, JSON parse re-validated, all pre-existing bytes untouched).

Why

GET /api/tasks/runs proxies Trigger.dev runs, which only carry taskIdentifier — and every scheduled prompt shares customer-prompt-task, so the chat homepage renders five identical "Scheduled Task" rows (recoupable/chat#1850, video-parity item 1). The api resolves each list-mode run's title by joining Trigger's filter[schedule] runs against the account's scheduled_actions (title + trigger_schedule_id). title is null when a run cannot be mapped to a scheduled task (e.g. non-scheduled runs), and is not present in retrieve mode (runId provided) — mirroring the schema's existing mode-scoped field notes.

Links

• Tracking: Valuation-first homepage (Catalog HQ): surface catalog value + task runs on chat home; fix the .dev cross-domain auth regression chat#1850 (Open — video/experience parity, item 1)
• Siblings: api implementation PR + chat render PR (linked from the tracking issue)
• Merge order: docs (this) → api → chat. Contract-first; the field is additive so docs landing first documents a field the api serves shortly after.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Task run responses now include an optional title field when available, helping identify the originating scheduled task in run listings.
  • If a scheduled task can’t be resolved, the field may be returned as null.

Summary by cubic

Adds a nullable title field to TaskRunResponse so run listings can show the originating scheduled task’s title. Improves readability of GET /api/tasks/runs by naming scheduled runs; the field is only in list mode, may be null if unresolved, and is omitted in retrieve mode.

^{Written for commit 83faa16. Summary will update on new commits.}